Repository navigation
feat(release): support source-only verification and forced planning - #499
Merged
Merged
Conversation
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
This was referenced Nov 7, 2026
Merged
neilime
force-pushed
the
feat/source-release-verification
branch
from
November 7, 2026 07:32
2edc872 to
88cfa15
Compare
neilime
commented
Nov 7, 2026
neilime
force-pushed
the
feat/source-release-verification
branch
from
November 7, 2026 07:48
88cfa15 to
d45f87c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Composer source releases have no uploaded package artifact. Allow
artifact-idsto be omitted or[], while retaining tag identity, publication state and API-error checks. Supplied artifacts must be unexpired and belong to the same workflow run and source commit.Add
forcetorelease/planso callers can release without relevant changes. Release Drafter's existing SDK calculates the version, tag and name from the configured rules and templates, including on no-change runs. Force only bypasses the no-change decision. Tag collisions and API errors still fail; planning never creates or moves tags. Callers decide which events may request force.Validation
This supports the prepare → validate → release journey in ci-github-php #1, without adding Composer package uploads or version commits.